Consolidated management of home network elements

ABSTRACT

Methods, systems, and computer readable media can be operable to facilitate the generation of a user interface displaying the devices associated with a local network. A client device may retrieve information associated with one or more devices associated with a common central device, local network, and/or subscriber. The client device may generate a user interface including one or more device objects organized along an ellipsoidal wireframe, wherein each device object represents an identified device. The user interface may include device identification and/or status information associated with each displayed device. Devices displayed within the user interface may be filtered based upon one or more parameters selected by a user. The client device may update and rearrange the displayed device objects based upon navigation commands received from a user via a control device.

CROSS REFERENCE TO RELATED APPLICATION

This application is a non-provisional application claiming the benefitof U.S. Provisional Application Ser. No. 62/110,092, entitled “UserInterface for Managing Networked Devices,” which was filed on Jan. 30,2015, and is incorporated herein by reference in its entirety.

TECHNICAL FIELD

This disclosure relates to the management of home network elements.

BACKGROUND

Typically, multiple services (e.g., video, voice, data, etc.) arereceived at a subscriber premise by a customer premise equipment (CPE)device (e.g., gateway device), and the multiple services are provided toconsumers over a local network (e.g., local area network (LAN), wirelesslocal area network (WLAN), multimedia over coax alliance (MoCA) network,etc.). Devices connected to the local network may be configured toreceive services offered by a service provider (e.g., multiple systemsoperator (MSO)) and may be configured to communicate with other devicesconnected to the local network.

The types of devices that may be connected to a local network continuesto grow in number. For example, local network access is not limited toonly multimedia devices (e.g., set-top boxes (STB), televisions, mobiledevices, tablets, etc.), but is now available to a multitude of otherhome and personal devices (e.g., Internet of things (IoT) devices) suchas appliances, wearables, home automation devices, and others.

However, subscribers are left without a means for viewing the breadth ofa local network and the various devices that are accessing or haveaccess to the local network. Moreover, there are currently no mechanismsavailable to allow a subscriber to view the various connections orpairings that may exist between devices within the subscriber premise.Therefore, it is desirable to provide a user interface through which asubscriber may view, manage, and interact with the plurality of devicesconnected to a local network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example network environmentoperable to facilitate the generation of a user interface displaying thedevices associated with a local network.

FIG. 2 is a block diagram illustrating an example client device operableto facilitate the generation of a user interface displaying the devicesassociated with a local network.

FIG. 3 is a flowchart illustrating an example process operable tofacilitate the generation of a user interface displaying the devicesassociated with a local network.

FIG. 4 is a flowchart illustrating an example process operable tofacilitate the generation of a user interface displaying subsidiarydevices associated with a selected client device.

FIG. 5 is an illustration of an example user interface operable tofacilitate the display of devices associated with a local network.

FIG. 6 is an illustration of an example user interface operable tofacilitate the display of subsidiary devices associated with a networkeddevice.

FIG. 7 is an illustration of an example user interface operable tofacilitate the expanded display of subsidiary devices associated with anetworked device.

FIG. 8 is a block diagram of a hardware configuration operable tofacilitate the generation of a user interface displaying the devicesassociated with a local network.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

It is desirable to improve upon methods and systems for monitoring,managing, and interfacing with devices associated with a common centraldevice, local network, and/or subscriber. The methods, systems, andcomputer readable media described herein can be operable to facilitatethe generation of a user interface displaying the devices associatedwith a local network. A client device may retrieve informationassociated with one or more devices associated with a common centraldevice, local network, and/or subscriber. The client device may generatea user interface including one or more device objects organized along anellipsoidal wireframe, wherein each device object represents anidentified device. The user interface may include device identificationand/or status information associated with each displayed device. Devicesdisplayed within the user interface may be filtered based upon one ormore parameters selected by a user. The client device may update andrearrange the displayed device objects based upon navigation commandsreceived from a user via a control device.

An embodiment of the invention described herein may include a methodcomprising: (a) identifying one or more devices of a group of networkeddevices, wherein each of the one or more devices within the group ofnetworked devices is associated with a common local network; (b)retrieving device information associated with one or more of the one ormore identified devices; (c) identifying one or more of the one or moreidentified devices for displaying within the user interface by filteringthe one or more identified devices according to one or more parameters;(d) associating each respective one of the one or more devicesidentified for displaying within the user interface with a respectivedevice object and a respective location within an ellipsoidal wireframe;and (e) outputting the user interface to a display, wherein the userinterface comprises each respective device object positioned at arespective location within the ellipsoidal wireframe.

According to an embodiment of the invention, the method described hereinmay further comprise the steps of: (a) determining that a respective oneof the one or more devices identified for displaying within the userinterface is associated with at least one subsidiary device; (b)retrieving information associated with the at least one subsidiarydevice; (c) associating each respective one of the at least onesubsidiary device with a subsidiary device icon; and (d) displaying eachsubsidiary device icon as an element rotating about a device iconassociated with the respective one device.

According to an embodiment of the invention, the method described hereinmay further comprise the steps of: (a) receiving a user selection of adevice object; (b) identifying one or more subsidiary devices that areassociated with the device associated with the selected device object;(c) associating each respective one of the one or more subsidiarydevices with a respective subsidiary device object and a respectivelocation within a secondary ellipsoidal wireframe; and (d) outputting asecondary user interface to a display, wherein the secondary userinterface comprises each respective subsidiary device object positionedat a respective location within the secondary ellipsoidal wireframe.

According to an embodiment of the invention, each respective one of theone or more devices identified for displaying within the user interfaceis associated with a device icon background color, the device iconbackground color being based upon a status of the respective device.

According to an embodiment of the invention, the method described hereinfurther comprises the steps of: (a) receiving a navigation command; and(b) rotating the positions of the device icons along the ellipsoidalwireframe in response to a direction indicated by the navigationcommand, such that a first device object located in a central locationalong the ellipsoidal wireframe prior to the navigation command beingreceived is replaced in the central location by a second device objectthat is positioned adjacent to the first object along the ellipsoidalwireframe.

According to an embodiment of the invention, the size of the seconddevice object is increased when the second device object is placed inthe central location along the ellipsoidal wireframe.

According to an embodiment of the invention, the method described hereinfurther comprises the steps of: (a) receiving a user selection of adevice object; (b) raising the position of the center of the ellipsoidalwireframe within the user interface; and (c) displaying one or moresecondary icons associated with the selected device object.

An embodiment of the invention described herein may include an apparatuscomprising: (a) one or more modules configured to: (i) identify one ormore devices of a group of networked devices, wherein each of the one ormore devices within the group of networked devices is associated with acommon local network; (ii) retrieve device information associated withone or more of the one or more identified devices; (iii) identify one ormore of the one or more identified devices for displaying within a userinterface by filtering the one or more identified devices according toone or more parameters; (iv) associate each respective one of the one ormore devices identified for displaying within the user interface with arespective device object and a respective location within an ellipsoidalwireframe; and (b) an interface configured to be used to output the userinterface to a display, wherein the user interface comprises eachrespective device object positioned at a respective location within theellipsoidal wireframe.

An embodiment of the invention described herein may include one or morenon-transitory computer readable media having instructions operable tocause one or more processors to perform the operations comprising: (a)identifying one or more devices of a group of networked devices, whereineach of the one or more devices within the group of networked devices isassociated with a common local network; (b) retrieving deviceinformation associated with one or more of the one or more identifieddevices; (c) identifying one or more of the one or more identifieddevices for displaying within the user interface by filtering the one ormore identified devices according to one or more parameters; (d)associating each respective one of the one or more devices identifiedfor displaying within the user interface with a respective device objectand a respective location within an ellipsoidal wireframe; and (e)outputting the user interface to a display, wherein the user interfacecomprises each respective device object positioned at a respectivelocation within the ellipsoidal wireframe.

FIG. 1 is a block diagram illustrating an example network environment100 operable to facilitate the generation of a user interface displayingthe devices associated with a local network. In embodiments, video,voice, and/or data services may be delivered to one or more clientdevices 105. Client devices 105 may include a television, mobile device,tablet, computer, set-top box (STB), gaming device, access points (APs),and any other device operable to receive video, voice, and/or dataservices. It should be understood that various services may be deliveredto the client devices 105, including but not limited to, live orbroadcast television, video-on-demand (VoD) content, pay-per viewcontent, recorded content (e.g., DVR content), audio-only content,streaming content such as YouTube or Netflix content, and other variousvideo, data, and/or voice services. It should be further understood thatthe devices shown in FIG. 1 may be integrated. For example, a televisionmay be connected to and controlled by a STB.

In embodiments, client devices 105 may include Internet of things (IoT)devices. For example, household devices appliances such asrefrigerators, temperature control elements, ovens, and any other devicewithin a subscriber premise that may communicate (e.g., over a wired orwireless interface) with one or more other client devices 105 or accesspoint.

Multiple services may be delivered to client devices 105 over a localnetwork 110. The local network 110 may include a local area network(LAN), wireless local area network (WLAN), personal area network (PAN),mobile hotspot network, and others. The local network 110 may beprovided at a subscriber premise by a central device 115. The centraldevice 115 may include a gateway device, modem device, combinationthereof or other access device. It will be appreciated by those skilledin the relevant art that delivery of the multiple services over thelocal network 110 may be accomplished using a variety of standards andformats.

In embodiments, one or more client devices 105 associated with asubscriber and/or premise may be referred to as a group of networkeddevices. For example, a group of networked devices may include each ofone or more client devices 105 that are serviced by a common centraldevice 115 or that are otherwise associated with a common local network110. The group of networked devices may further include any subsidiarydevice associated with a client device 105 that is service by the commoncentral device 115. For example, subsidiary devices may include devicesthat are configured to communicate with a client device 105 but that arenot configured to communicate with a central device servicing the clientdevice 105. Subsidiary devices may include, but are not limited toprinters, scanners, cameras, remote control units (RCUs), projectors,servers, and others.

In embodiments, multiple services (e.g., video, voice, and/or dataservices) may be delivered from a wide-area network (WAN) 120 to thelocal network 110 through a connection to a subscriber network 125. Thesubscriber network 125 may include an optical network, hybrid fibercoaxial (HFC) network, twisted-pair, mobile network, high-speed datanetwork, satellite network, and others. Multiple systems operator (MSO)devices and/or networks within the WAN 120 may be used to provide,manage, and/or troubleshoot the multiple services provided tosubscribers.

It will be appreciated by those skilled in the relevant art that clientdevices 105 may be capable of interacting and communicating with eachother and/or with a central device 115 over various wirelesscommunication standards (e.g., Wi-Fi, Zigbee, Bluetooth, etc.) or wiredcommunication standards (e.g., Ethernet, Multimedia over Coax Alliance(MoCA), etc.). Client devices 105 connected to a local network 110 mayreceive services according to one or more subscriptions entered intobetween a subscriber and service provider.

In embodiments, a client device 105 (e.g., STB) may be configured toprovide a subscriber with an interface for monitoring and/or managingclient devices 105 making up a group of networked devices. For example,a subscriber may request the interface through a STB, and the STB mayoutput the interface to a display device (e.g., television) associatedwith the STB. The subscriber may initiate the generation of theinterface and may control and navigate the interface using a controlunit (e.g., RCU) associated with the STB.

A STB may be configured to identify each of one or more client devices105 within a group of networked devices associated with a common centraldevice 115 and/or a subscriber initiating the interface generation. Inembodiments, the central device 115 can maintain a list of clientdevices 105 that are connected to the central device 115, are servicedby the central device 115, and/or are otherwise associated with a commonpremise, subscription, and/or subscriber. For example, the centraldevice 115 can periodically request connection updates from clientdevices 105 or can receive a notification when a client device 105 joinsthe local network 110.

The STB may be configured to retrieve various other informationassociated with client device(s) 105 making up the group of networkeddevices. For example, the central device 115 may store or otherwiseaccess information associated with client devices 105 under the controlof a subscriber, content provided to the client devices 105, andsubscription information associated with the client devices 105. Itshould be understood that the information identifying content providedto client devices and/or subscription information may be located at anetwork back office (e.g., server or application connected to the WAN120), or may be located within a subscriber premise (e.g., server orapplication connected to the local network 110).

The STB may retrieve status information associated with client device(s)105 making up the group of networked devices. The central device 115 maymaintain and/or access current status information associated with eachclient device 105 (e.g., power state, tuning state, content displayed,wireless capability/availability, etc.). For example, the central device115 may periodically request state information and/or tuning/contentinformation from each of the client devices 105 or the central device115 may receive status updates from a client device when the clientdevice experiences a power state change (e.g., powers up or down) orwhen the client device tunes to a different channel or content source.It will be appreciated by those skilled in the relevant art that thecentral device 115 can use various communication techniques and methodsto maintain a current list of client devices and corresponding statusinformation.

The STB may retrieve subscription information associated with clientdevice(s) 105 making up the group of networked devices. The centraldevice 115 may maintain subscription information associated with one ormore client devices 105 or a subscriber associated with the clientdevices 105. For example, the central device 115 may have access tosubscription information (e.g., internally or through a connection to anexternal server), and can determine what services and/or programming isavailable to a client device 105 or subscriber by looking up thecorresponding subscription information.

In embodiments, the STB may generate a user interface that displays to aviewer an identifier of each of the client devices 105 making up thegroup of networked devices. Devices that are connected and networkedtogether may be displayed in a mixed icon/text/background style, whereinthe icon/text/background describes or suggests the identity,functionality, and/or status of each of the one or more client devices105 making up the group of networked devices. Each client device 105 maybe displayed in the user interface as an object, and each object caninclude various components serving to describe the identity,functionality, status, and/or other characteristics of the device. Theobject may include an icon associated with the type of device (e.g.,gateway, set-top box (STB), gaming device, mobile device, etc.). Theobject may include text describing the type of device, an identifier orname of the device (e.g., a name assigned to the device by auser/owner), a user associated with the device, and/or othercharacteristics. The object may include a background associated with thestatus of the device. For example, the background may be coloredaccording to whether the device is active/inactive,connected/disconnected, on/off, wirelessly enabled/disabled, oraccording to other status information.

The device objects may be organized in the user interface in such a wayas to allow a subscriber to view all of the client devices 105 connectedto a network (e.g., local network 110) and to navigate through each ofthe displayed devices. For example, an ellipsoidal wireframe may be usedto define locations for display of the device objects (e.g.,icon/text/background combinations) in a three-dimensional perspective.The ellipsoidal wireframe may provide a skeleton for icon placementwithin a user interface and may be in the shape of an ellipse. Thewireframe may be provided with a depth aspect such that the ellipseappears in the user interface as an ellipsoid. In embodiments, theellipsoidal wireframe may be an adjusting wireframe. For example, thewireframe may be rotated according to user interaction with the userinterface. A user may navigate the user interface via a RCU associatedwith the STB, and the user interface may provide the user with optionsfor managing, configuring, and interacting with the client devices 105represented by the various device objects.

In embodiments, the user interface may include one or more sub-layers.For example, a client device 105 represented by a device object within aprimary layer of the user interface may be associated with one or moresubsidiary devices (e.g., printers, scanners, cameras, RCUs, projectors,servers, etc.), and when a user selects the device object representingthe client device 105, a sub-layer of the user interface including adisplay of one or more device objects representing the one or moresubsidiary devices may be presented to the user.

FIG. 2 is a block diagram illustrating an example client device 105operable to facilitate the generation of a user interface displaying thedevices associated with a local network. The client device 105 may be aSTB, or any other device configured to output a user interfacedisplaying one or more client devices 105 associated with a commoncentral device 115 of FIG. 1 or local network 110 of FIG. 1. The clientdevice 105 may include a control interface 205, a device management menumodule 210, a network interface 215, and a display interface 220. Inembodiments, the device management menu module 210 may reside within theclient device 105, a central device 115, a server or application atanother device within a premise or local network, a server orapplication within an upstream network (e.g., subscriber network 125 ofFIG. 1, WAN 120 of FIG. 1, etc.), or any other suitable location.

In embodiments, the client device 105 may be configured to provide asubscriber with an interface for monitoring and/or managing devicesmaking up a group of networked devices. For example, the client device105 may receive a subscriber request for the interface through a controlinterface 205, and the client device 105 may output the interface to adisplay device (e.g., television) through a display interface 220. Thesubscriber may initiate the generation of the interface and may controland navigate the interface using a control unit (e.g., RCU) associatedwith the client device 105. For example, the client device 105 mayreceive initiation and control commands from the control unit throughthe control interface 205.

When a request for the interface is received at the client device 105, adevice management menu module 210 may identify each of one or moredevices (e.g., client devices 105, central device 115 of FIG. 1,subsidiary devices, etc.) within a group of networked devices associatedwith a common central device 115 and/or a subscriber initiating theinterface generation. In embodiments, the central device 115 canmaintain a list of client devices 105 that are connected to the centraldevice 115, are serviced by the central device 115, and/or are otherwiseassociated with a common premise, subscription, and/or subscriber. Theclient device 105 may request and receive information associated witheach device within the group of networked devices from the centraldevice 115, or other device or server, through the network interface215. Information associated with a device may include a uniqueidentifier (e.g., device type, device model number, personalized devicename, etc.), status information (e.g., power state, tuning state,content displayed, wireless capability/availability, etc.), and/or otherdevice information.

In embodiments, the device management menu module 210 may generate auser interface that displays to a viewer an identifier of each of thedevices making up the group of networked devices. Each device may bedisplayed in the user interface as an object, and each object caninclude various components serving to describe the identity,functionality, status, and/or other characteristics of the device. Theobject may include an icon associated with the type of device (e.g.,gateway, set-top box (STB), gaming device, mobile device, etc.). Theobject may include text describing the type of device, an identifier orname of the device (e.g., a name assigned to the device by auser/owner), a user associated with the device, and/or othercharacteristics. The object may include a background associated with thestatus of the device. For example, the background may be coloredaccording to whether the device is active/inactive,connected/disconnected, on/off, wirelessly enabled/disabled, or otherstatus information.

The device management menu module 210 may organize the device objects inthe user interface in such a way as to allow a subscriber to view all ofthe devices connected to a network (e.g., local network 110 of FIG. 1)and to navigate through each of the displayed devices. For example, anellipsoidal wireframe may be used to define locations for display of thedevice objects (e.g., icon/text/background combinations) in athree-dimensional perspective. The user interface may provide the userwith options for managing, configuring, and interacting with the devicesrepresented by the various device objects.

In embodiments, the device management menu module 210 may retrieveinformation associated with one or more subsidiary devices associatedwith one or more of the networked devices, and the device managementmenu module 210 may generate one or more sub-layers associated with theuser interface. For example, a device represented by a device objectwithin a primary layer of the user interface may be associated with oneor more subsidiary devices (e.g., printers, scanners, cameras, RCUs,projectors, servers, etc.), and when a user selects the device objectrepresenting the primary device, a sub-layer of the user interfaceincluding a display of one or more device objects representing the oneor more subsidiary devices may be output to a display device through thedisplay interface 220.

FIG. 3 is a flowchart illustrating an example process 300 operable tofacilitate the generation of a user interface displaying the devicesassociated with a local network. The process 300 can begin at 305, whena request for a consolidated device interface is received. The requestfor the consolidated device interface may be received at a client device105 of FIG. 1 such as a STB.

At 310, one or more devices (e.g., central device 115 of FIG. 1, clientdevices 105, subsidiary devices, etc.) that are within a group ofnetworked devices may be identified. The one or more devices within agroup of networked devices may be identified, for example, by a STBreceiving the request for the consolidated device interface. Inembodiments, the group of networked devices may include one or moreclient devices 105 connected to and/or serviced by one or moreassociated central devices 115, one or more client devices 105 connectedto a common network (e.g., local network 110 of FIG. 1), and/or one ormore client devices 105 associated with a common subscription,subscriber, and/or premise. Associations between client devices 105,central devices 115, local networks 110, and subscription services maybe stored at and retrieved from a central device 115 serving the STB. Itshould be understood that the associations between client devices 105,central devices 115, local networks 110, and subscription services maybe stored at and retrieved from various other devices (e.g., CPEdevices, client devices, etc.) and/or servers (e.g., upstream networkservers, servers internal to a subscriber premise, etc.).

At 315, the determination may be made whether a user filter is selectedfor application to the one or more identified devices. The determinationwhether a user filter is selected may be made, for example, by a devicemanagement menu module 210 of FIG. 2. In embodiments, a specific userassociated with the request for the consolidated device interface may beidentified. For example, the specific user may be identified from therequest for the consolidated device interface, may be determined basedupon a default setting at the STB, or may be determined based upon inputreceived from the user.

If, at 315, the determination is made that a user filter is selected,the process 300 may proceed to 320. At 320, the one or more identifieddevices may be filtered according to the selected user filter. Inembodiments, the STB (e.g., at a device management menu module 210) maymaintain a list of identified devices making up a group of networkeddevices, and one or more of the identified devices may be associatedwith one or more specific users. The STB may remove from the list ofidentified devices any device that is not associated with the useridentified by the selected user filter.

If, at 315, the determination is made that no user filter is selected,the process 300 may proceed to 325. At 325, the determination may bemade whether a device category filter is selected for application to theone or more identified devices. The determination whether a devicecategory filter is selected may be made, for example, by a devicemanagement menu module 210 of FIG. 2. In embodiments, each of theidentified client devices 105 may be associated with one or morecategories (e.g., device type, wireless capability, service type, etc.),and a specific category may be selected by a user for use in populatinga list of client devices 105. A category selection may be identifiedfrom the request for the consolidated device interface, may bedetermined based upon a default setting at the STB, or may be determinedbased upon input received from the user.

If, at 325, the determination is made that a device category filter isselected, the process 300 may proceed to 330. At 330, the one or moreidentified devices may be filtered according to the selected devicecategory filter. In embodiments, the STB (e.g., at a device managementmenu module 210) may maintain a list of identified devices making up agroup of networked devices, and one or more of the identified devicesmay be associated with one or more categories. The STB may remove fromthe list of identified devices any device that is not associated withthe category identified by the selected device category filter.

If, at 325, the determination is made that a device category filter isnot selected, the process 300 may proceed to 335. At 335, each of theidentified devices, or identified devices that remain after filteringaccording to a selected user filter and/or device category filter, maybe associated with a position within an ellipsoidal wireframe. Theidentified devices may be associated with ellipsoidal wireframepositions, for example, by the device management menu module 210. Inembodiments, each of the identified devices may be associated with anicon (e.g., a display icon indicating a device type such as television,tablet, access point, computer, IoT device, etc.), and the devicemanagement menu module 210 may generate a user interface (e.g.,graphical user interface (GUI)) that includes the one or more iconsradially positioned along an ellipsoidal wireframe. The user interfacemay further include an identification of and an option for changing aselected user filter, device category filter, and various otherinformation and filter settings associated with the user interface. Theellipsoidal wireframe may be output within the user interface to adisplay (e.g., display device such as a television connected to the STB)at 340.

FIG. 4 is a flowchart illustrating an example process 400 operable tofacilitate the generation of a user interface displaying subsidiarydevices associated with a selected client device. The process 400 canbegin at 405, when a user selection of a networked device (e.g., clientdevice 105 of FIG. 1) is received. The user selection of a networkeddevice may be received at a client device 105 of FIG. 1 such as a STB.In embodiments, the selection of the networked device may be a selectionof an icon associated with the networked device from an ellipsoidalwireframe displayed within a user interface that is output from the STBto a display.

At 410, the determination may be made whether one or more subsidiarydevices are associated with the selected device. An association betweenthe selected device and one or more subsidiary devices may be indicatedto a user by displaying one or more icons associated with the one ormore subsidiary devices surrounding the icon representing the selecteddevice in the user interface. The STB, or another client device 105 orcentral device 115 of FIG. 1 may maintain associations between anetworked device and subsidiary device(s). For example, thedetermination whether one or more subsidiary devices are associated withthe selected device may be made by the device management menu module 210of FIG. 2.

If, at 410, the determination is made that no subsidiary devices areassociated with the selected device, the process 400 may proceed to 415.At 415, one or more management options associated with the selecteddevice may be output to a display within a user interface. For example,the STB may output an interface that includes one or more userselectable options for viewing device details associated with theselected device, configuring the selected device (e.g., power up/down,configuring wireless settings, etc.), or otherwise interacting with theselected device.

If, at 410, the determination is made that at least one subsidiarydevice is associated with the selected device, the process 400 mayproceed to 420. At 420, each of the one or more subsidiary devices maybe associated with a position within a secondary ellipsoidal wireframe.The one or more subsidiary devices may be associated with ellipsoidalwireframe positions, for example, by the device management menu module210. In embodiments, each of the one or more subsidiary devices may beassociated with an icon (e.g., a display icon indicating a device typesuch as printer, scanner, camera, RCU, etc.), and the device managementmenu module 210 may generate a user interface (e.g., graphical userinterface (GUI)) that includes the one or more icons radially positionedalong a secondary ellipsoidal wireframe. The secondary ellipsoidalwireframe may be output within the user interface to a display (e.g.,display device such as a television connected to the STB) at 425.

FIG. 5 is an illustration of an example user interface 500 operable tofacilitate the display of devices associated with a local network. Theuser interface 500 may be generated by a client device (e.g., clientdevice 105 of FIG. 1 such as a STB), a central device 115 of FIG. 1(e.g., gateway device), an upstream network device (e.g., externalserver, or any other device. In embodiments, the user interface 500 maybe output from a STB and displayed at a display device (e.g.,television, tablet, mobile device, etc.) associated with the STB. Itwill be appreciated by those skilled in the relevant art that the userinterface 500 may be displayed to a subscriber using various interfacetypes (e.g., graphical user interface (GUI), touch-screen interface,etc.).

In embodiments, one or more device icons 505 representing devices thatare connected and/or networked together may be displayed along anellipsoidal wireframe 510 in the user interface 500. The devicesrepresented by device icons 505 in the user interface 500 may includeeach of one or more client devices 105, central device 115, and/orsubsidiary devices making up a group of networked devices (e.g., devicesconnected to a common central device 115 and/or common local network 110of FIG. 1).

In embodiments, the device icon 505 may be an image that describes orsuggests the device identity, functionality, and/or status. For example,each device icon 505 may be an icon associated with the type of device(e.g., gateway, set-top box (STB), gaming device, mobile device, etc.)that is represented by the device icon 505. In embodiments, each deviceicon 505 may be associated with a textual identifier 515, wherein thetextual identifier 515 describes a device type associated with thedevice represented by the device icon 505, a name of the device (e.g., aname assigned to the device by a user/owner), a user associated with thedevice, or other characteristic(s).

In embodiments, the device icon 505 may include a background associatedwith the status of the device represented by the device icon 505. Forexample, the background may be colored according to whether the deviceis active/inactive, connected/disconnected, on/off, or according toother status or configuration information. As another example, thedevice icon 505 may include a symbol designated to indicate when thedevice represented by the device icon 505 is capable of receiving and/ortransmitting wireless communications (e.g., Wi-Fi symbols) and whetheror not the device is successfully paired with another device via awireless connection (e.g., Wi-Fi connection, Bluetooth connection,etc.).

The device icons 505 may be radially spread along the ellipsoidalwireframe 510. For example, locations along the ellipsoidal wireframe510 may be designated for the display of the device icons 505 in athree-dimensional perspective. A three-dimensional perspective may becreated by reducing the size of device icons 505 and correspondingtextual identifiers 515 as the device icons 505 and textual identifiers515 are moved from the bottom of the user interface 500 toward the topof the user interface 500. For example, the front (i.e., bottom) deviceicon 505 may be the largest device icon 505, and the back (i.e., top)device icon 505 may be the smallest device icon 505.

In embodiments, a user may navigate through the device icons 505 byrotating the positions of the displayed device icons 505 around theellipsoidal wireframe 510. For example, a user may navigate through thedevice icons 505 using a RCU that interfaces with a STB through whichthe user interface 500 is output. Navigation to the right or to the leftmoves all device icons 505 one location along the ellipsoid border tothe left or right respectively, and brings the next, adjacent deviceicon 505 to the front/center of the user interface 500. Each time theellipsoid is rotated to account for a navigation step, the size of alldevice icons 505 may be changed to maintain the three-dimensionalperspective on the user interface 500.

In embodiments, the device icon 505 in the front/center location alongthe ellipsoidal wireframe 510 (e.g., the position of the “STB” as shownin FIG. 5) may be designated as the subject device. For example, a usermay initiate a further inspection, configuration, or other interactionwith the subject device by pressing a pre-defined button (e.g., select,enter, etc.) of a control device associated with the device throughwhich the user interface 500 is displayed. In embodiments, variousproperties of the subject device icon 505 may be emphasized over otherdevice icons 505. For example, the subject device icon 505 may be largerthan the other device icons 505, may be colored differently or brighterthan the other device icons 505, or other properties may be emphasized.In embodiments, an indentation or arrow on the line creating theellipsoidal wireframe 510 border may be positioned below the subjectdevice icon 505 and may point to the subject device icon 505.

In embodiments, device and configuration information associated with adevice represented by a device icon 505 may be displayed within a devicesummary/information text box 520 of the user interface 500. For example,device and configuration information associated with a subject deviceicon 505 may be displayed after the subject device icon 505 has beenpositioned at the front of the ellipsoidal adjusting wireframe 510 for apredetermined duration of time (e.g., 1 second, 2 seconds, etc.) or maybe displayed after a user initiates a request (e.g., via a requestreceived from a RCU) for the device and/or configuration informationassociated with the subject device icon 505. In embodiments, textdescribing what functions are available to the user, what specific RCUkeys may be used to activate certain functions, instructions fornavigating the user interface 500, and other information may bedisplayed to a user within the device summary/information text box 520.

When a device icon 505 located in the forward-most position of theellipsoidal adjusting wireframe 510 (e.g., the subject device icon 505)is selected for configuration and/or retrieval of additional deviceinformation, the entire ellipsoidal adjusting wireframe 510, along witheach of the device icons 505 may be raised or shifted up in the userinterface 500 to make room for the display of additional secondary icons(e.g., icons linking to categories of additional device configuration orinformation) and/or device information at the position of the devicesummary information 520.

In embodiments, the devices included in the interface may be filteredaccording to various categories (e.g., “All Devices,” “Wired Devices,”“Wireless Devices,” “IoT Devices,” etc.). For example, the userinterface 500 may include device category filters 525, and a user mayselect a device category filter to apply to the devices that areorganized along the ellipsoidal wireframe 510. A device category filter525 that is selected by a user may be emphasized over the other devicecategory filters 525. For example, the selected device category filter525 (e.g., “ALL DEVICES” is the selected device category filter 525 inFIG. 5) may be colored or sized differently than the other devicecategory filters 525 or may be given a different size or color borderthan the others. When, the selected device category filter 525 ischanged, the device icons 505 included on the ellipsoidal wireframe 510may be updated to include only those device icons 505 that representdevices that are included within the selected device category filter525.

In embodiments, the devices included in the user interface 500 may befiltered according to a user filter. For example, the user interface 500may include an identification of a current user and an option to changethe current user (e.g., user identifier 530). The device icons 505located around the ellipsoidal wireframe 510 may include only thosedevice icons 505 that represent devices that are associated with theselected user as identified by the user identifier 530.

FIG. 6 is an illustration of an example user interface 600 operable tofacilitate the display of subsidiary devices associated with a networkeddevice. In embodiments, the user interface 600 may include one or moresubsidiary device icons 605 representing a subsidiary device (e.g., adevice connected to a network solely via another device) that isassociated with a device represented by a device icon 505 that ispositioned on an ellipsoidal wireframe 510. One or more subsidiarydevice icons 605 may be displayed within the user interface 600 as acluster of icons orbiting around the device icon 505 representing thenetworked device with which the subsidiary devices are associated (e.g.,the device through which the subsidiary device is connected to thenetwork). In embodiments, an orbit of subsidiary device icons 605 may beexpanded into a full ellipse upon being selected for further examinationand collapsed back upon deselection. As an example, subsidiary deviceicons 605 representing Internet of things (IoT) devices may be shownorbiting an associated networked device. Information associated withsubsidiary devices may be retrieved from the networked device (e.g.,client device 105 of FIG. 1) with which the subsidiary devices areassociated or from a central device (e.g., central device 115 of FIG.1).

FIG. 7 is an illustration of an example user interface 700 operable tofacilitate the expanded display of subsidiary devices associated with anetworked device. Subsidiary device icons 605 representing subsidiarydevices that are associated with a networked device may be spread alongan ellipsoidal wireframe 510. A textual identifier 705 may provide anidentification of a subsidiary device (e.g., device type, unique namegiven to the device, etc.). In embodiments, a device icon 505representing the networked device may be displayed within the center ofthe ellipsoidal wireframe 510.

FIG. 8 is a block diagram of a hardware configuration 800 operable tofacilitate the generation of a user interface displaying the devicesassociated with a local network. The hardware configuration 800 caninclude a processor 810, a memory 820, a storage device 830, and aninput/output device 840. Each of the components 810, 820, 830, and 840can, for example, be interconnected using a system bus 850. Theprocessor 810 can be capable of processing instructions for executionwithin the hardware configuration 800. In one implementation, theprocessor 810 can be a single-threaded processor. In anotherimplementation, the processor 810 can be a multi-threaded processor. Theprocessor 810 can be capable of processing instructions stored in thememory 820 or on the storage device 830.

The memory 820 can store information within the hardware configuration800. In one implementation, the memory 820 can be a computer-readablemedium. In one implementation, the memory 820 can be a volatile memoryunit. In another implementation, the memory 820 can be a non-volatilememory unit.

In some implementations, the storage device 830 can be capable ofproviding mass storage for the hardware configuration 800. In oneimplementation, the storage device 830 can be a computer-readablemedium. In various different implementations, the storage device 830can, for example, include a hard disk device, an optical disk device,flash memory or some other large capacity storage device. In otherimplementations, the storage device 830 can be a device external to thehardware configuration 800.

The input/output device 840 provides input/output operations for thehardware configuration 800. In embodiments, the input/output device 840can include one or more of a network interface device (e.g., an Ethernetcard), a serial communication device (e.g., an RS-232 port), one or moreuniversal serial bus (USB) interfaces (e.g., a USB 2.0 port), one ormore wireless interface devices (e.g., an 802.11 card), and/or one ormore interfaces for outputting video and/or data services to a clientdevice 105 of FIG. 1 (e.g., television, computer, tablet, mobile device,etc.) or central device 115 of FIG. 1 (e.g., gateway device, cablemodem, server, etc.). In embodiments, the input/output device caninclude driver devices configured to send communications to, and receivecommunications from one or more networks (e.g., local network 110 ofFIG. 1, subscriber network 125 of FIG. 1, WAN 120 of FIG. 1, etc.).

Those skilled in the art will appreciate that the invention improvesupon methods and systems for monitoring, managing, and interfacing withdevices associated with a common central device, local network, and/orsubscriber. Methods, systems, and computer readable media can beoperable to facilitate the generation of a user interface displaying thedevices associated with a local network. A client device may retrieveinformation associated with one or more devices associated with a commoncentral device, local network, and/or subscriber. The client device maygenerate a user interface including one or more device objects organizedalong an ellipsoidal wireframe, wherein each device object represents anidentified device. The user interface may include device identificationand/or status information associated with each displayed device. Devicesdisplayed within the user interface may be filtered based upon one ormore parameters selected by a user. The client device may update andrearrange the displayed device objects based upon navigation commandsreceived from a user via a control device.

The subject matter of this disclosure, and components thereof, can berealized by instructions that upon execution cause one or moreprocessing devices to carry out the processes and functions describedabove. Such instructions can, for example, comprise interpretedinstructions, such as script instructions, e.g., JavaScript orECMAScript instructions, or executable code, or other instructionsstored in a computer readable medium.

Implementations of the subject matter and the functional operationsdescribed in this specification can be provided in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Embodiments ofthe subject matter described in this specification can be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a tangible program carrier forexecution by, or to control the operation of, data processing apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, or declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program can bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program can be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification areperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output thereby tying the process to a particular machine(e.g., a machine programmed to perform the processes described herein).The processes and logic flows can also be performed by, and apparatuscan also be implemented as, special purpose logic circuitry, e.g., anFPGA (field programmable gate array) or an ASIC (application specificintegrated circuit).

Computer readable media suitable for storing computer programinstructions and data include all forms of non-volatile memory, mediaand memory devices, including by way of example semiconductor memorydevices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks(e.g., internal hard disks or removable disks); magneto optical disks;and CD ROM and DVD ROM disks. The processor and the memory can besupplemented by, or incorporated in, special purpose logic circuitry.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinvention or of what may be claimed, but rather as descriptions offeatures that may be specific to particular embodiments of particularinventions. Certain features that are described in this specification inthe context of separate embodiments can also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment can also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination can in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a sub combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems cangenerally be integrated together in a single software product orpackaged into multiple software products.

Particular embodiments of the subject matter described in thisspecification have been described. Other embodiments are within thescope of the following claims. For example, the actions recited in theclaims can be performed in a different order and still achieve desirableresults, unless expressly noted otherwise. As one example, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or sequential order, to achieve desirableresults. In some implementations, multitasking and parallel processingmay be advantageous.

We claim:
 1. A method of generating a user interface, the methodcomprising: identifying one or more devices of a group of networkeddevices, wherein each of the one or more devices within the group ofnetworked devices is associated with a common local network; retrievingdevice information associated with one or more of the one or moreidentified devices; identifying one or more of the one or moreidentified devices for displaying within the user interface by filteringthe one or more identified devices according to one or more parameters;associating each respective one of the one or more devices identifiedfor displaying within the user interface with a respective device objectand a respective location within an ellipsoidal wireframe; determiningthat a respective one of the one or more devices identified fordisplaying within the user interface is associated with at least onesubsidiary device; retrieving information associated with the at leastone subsidiary device; associating each respective one of the at leastone subsidiary device with a subsidiary device icon; and outputting theuser interface to a display, wherein the user interface comprises eachrespective device object positioned at a respective location within theellipsoidal wireframe, and wherein the user interface comprises adynamic display of each respective one subsidiary device icon as anelement rotating about a device icon that is associated with a devicewhich is associated with the subsidiary device associated with therespective one subsidiary device icon.
 2. The method of claim 1, furthercomprising: receiving a user selection of a device object; identifyingone or more subsidiary devices that are associated with the deviceassociated with the selected device object; associating each respectiveone of the one or more subsidiary devices with a respective subsidiarydevice object and a respective location within a secondary ellipsoidalwireframe; and outputting a secondary user interface to a display,wherein the secondary user interface comprises each respectivesubsidiary device object positioned at a respective location within thesecondary ellipsoidal wireframe.
 3. The method of claim 1, wherein eachrespective one of the one or more devices identified for displayingwithin the user interface is associated with a device icon backgroundcolor, the device icon background color being based upon a status of therespective device.
 4. The method of claim 1, further comprising:receiving a navigation command; and rotating the positions of the deviceicons along the ellipsoidal wireframe in response to a directionindicated by the navigation command, such that a first device objectlocated in a central location along the ellipsoidal wireframe prior tothe navigation command being received is replaced in the centrallocation by a second device object that is positioned adjacent to thefirst object along the ellipsoidal wireframe.
 5. The method of claim 4,wherein the size of the second device object is increased when thesecond device object is placed in the central location along theellipsoidal wireframe.
 6. The method of claim 1, further comprising:receiving a user selection of a device object; raising the position ofthe center of the ellipsoidal wireframe within the user interface; anddisplaying one or more secondary icons associated with the selecteddevice object.
 7. An apparatus comprising: one or more modulesconfigured to: identify one or more devices of a group of networkeddevices, wherein each of the one or more devices within the group ofnetworked devices is associated with a common local network; retrievedevice information associated with one or more of the one or moreidentified devices; identify one or more of the one or more identifieddevices for displaying within a user interface by filtering the one ormore identified devices according to one or more parameters; associateeach respective one of the one or more devices identified for displayingwithin the user interface with a respective device object and arespective location within an ellipsoidal wireframe; determine that arespective one of the one or more devices identified for displayingwithin the user interface is associated with at least one subsidiarydevice; retrieve information associated with the at least one subsidiarydevice; associate each respective one of the at least one subsidiarydevice with a subsidiary device icon; an interface configured to be usedto output the user interface to a display, wherein the user interfacecomprises each respective device object positioned at a respectivelocation within the ellipsoidal wireframe, and wherein the userinterface comprises a dynamic display of each respective one subsidiarydevice icon as an element rotating about a device icon that isassociated with a device which is associated with the subsidiary deviceassociated with the respective one subsidiary device icon.
 8. Theapparatus of claim 7, wherein the one or more modules are furtherconfigured to: when a device object is selected, identify one or moresubsidiary devices that are associated with the device associated withthe selected device object; associate each respective one of the one ormore subsidiary devices with a respective subsidiary device object and arespective location within a secondary ellipsoidal wireframe; and causethe interface to output a secondary user interface to a display, whereinthe secondary user interface comprises each respective subsidiary deviceobject positioned at a respective location within the secondaryellipsoidal wireframe.
 9. The apparatus of claim 7, wherein eachrespective one of the one or more devices identified for displayingwithin the user interface is associated with a device icon backgroundcolor, the device icon background color being based upon a status of therespective device.
 10. The apparatus of claim 7, wherein the one or moremodules are further configured to rotate the positions of the deviceicons along the ellipsoidal wireframe in response to a directionindicated by a received navigation command, such that a first deviceobject located in a central location along the ellipsoidal wireframeprior to the navigation command being received is replaced in thecentral location by a second device object that is positioned adjacentto the first object along the ellipsoidal wireframe.
 11. The apparatusof claim 7, wherein the one or more modules are further configured to:when a user selection of a device object is received, raise the positionof the center of the ellipsoidal wireframe within the user interface;and cause the interface to output, within the user interface, a displayof one or more secondary icons associated with the selected deviceobject.
 12. One or more non-transitory computer readable media havinginstructions operable to cause one or more processors to perform theoperations comprising: identifying one or more devices of a group ofnetworked devices, wherein each of the one or more devices within thegroup of networked devices is associated with a common local network;retrieving device information associated with one or more of the one ormore identified devices; identifying one or more of the one or moreidentified devices for displaying within the user interface by filteringthe one or more identified devices according to one or more parameters;associating each respective one of the one or more devices identifiedfor displaying within the user interface with a respective device objectand a respective location within an ellipsoidal wireframe; determiningthat a respective one of the one or more devices identified fordisplaying within the user interface is associated with at least onesubsidiary device; retrieving information associated with the at leastone subsidiary device; associating each respective one of the at leastone subsidiary device with a subsidiary device icon; and outputting theuser interface to a display, wherein the user interface comprises eachrespective device object positioned at a respective location within theellipsoidal wireframe, and wherein the user interface comprises adynamic display of each respective one subsidiary device icon as anelement rotating about a device icon that is associated with a devicewhich is associated with the subsidiary device associated with therespective one subsidiary device icon.
 13. The one or morenon-transitory computer-readable media of claim 12, wherein theinstructions are further operable to cause the one or more processors toperform the operations comprising: receiving a user selection of adevice object; identifying one or more subsidiary devices that areassociated with the device associated with the selected device object;associating each respective one of the one or more subsidiary deviceswith a respective subsidiary device object and a respective locationwithin a secondary ellipsoidal wireframe; and outputting a secondaryuser interface to a display, wherein the secondary user interfacecomprises each respective subsidiary device object positioned at arespective location within the secondary ellipsoidal wireframe.
 14. Theone or more non-transitory computer-readable media of claim 12, whereineach respective one of the one or more devices identified for displayingwithin the user interface is associated with a device icon backgroundcolor, the device icon background color being based upon a status of therespective device.
 15. The one or more non-transitory computer-readablemedia of claim 12, wherein the instructions are further operable tocause the one or more processors to perform the operations comprising:receiving a navigation command; and rotating the positions of the deviceicons along the ellipsoidal wireframe in response to a directionindicated by the navigation command, such that a first device objectlocated in a central location along the ellipsoidal wireframe prior tothe navigation command being received is replaced in the centrallocation by a second device object that is positioned adjacent to thefirst object along the ellipsoidal wireframe.
 16. The one or morenon-transitory computer-readable media of claim 15, wherein the size ofthe second device object is increased when the second device object isplaced in the central location along the ellipsoidal wireframe.
 17. Theone or more non-transitory computer-readable media of claim 12, whereinthe instructions are further operable to cause the one or moreprocessors to perform the operations comprising: receiving a userselection of a device object; raising the position of the center of theellipsoidal wireframe within the user interface; and displaying one ormore secondary icons associated with the selected device object.